How to use API Keys
To enhance the security and reliability of your integrations, Safe Infrastructure uses authenticated API access. Authenticated requests ensure that only authorized applications and developers can interact with our services, protecting your data and the overall ecosystem.
Authenticated requests receive higher rate limits and dedicated quotas. See Pricing & Plans for details on what each plan includes.
This guide explains how to generate an API key, use it for authenticated requests, and handle rate limits, errors, and security best practices.
Getting a Safe API Key
- Visit the developer dashboard (opens in a new tab).
- Create an account (if you haven't already).
- Generate your API key in the API Keys section.
The API Key is a JWT, which is set to expire after 5 years.
Using Your API Key
To authenticate your requests, include your API key in the Authorization header. Below, there are different request examples. We use EIP3770 names for chains, so for example, for Ethereum Mainnet (eth):
_10 curl -X GET "https://api.safe.global/tx-service/eth/api/v2/safes/0x5298a93734c3d979ef1f23f78ebb871879a21f22/multisig-transactions" \_10 -H "Authorization: Bearer $YOUR_API_KEY"
Rate Limits and Usage Tiers
Rate limits and monthly quotas depend on your plan:
| Plan | Sustained RPS | Monthly quota |
|---|---|---|
| Unauthenticated | 2 | 5,000 API units |
| Builder (Free) | 5 | 50,000 API units |
| Growth (€199/mo) | 15 | 1,000,000 API units |
| Scale (€499/mo) | 50 | 3,000,000 API units |
For full details on enforcement behavior when limits are reached, see Quotas & Limits.
Error Handling
If your API key is invalid or exceeds its rate limit, the API returns standard HTTP error codes:
401 Unauthorized: Invalid or missing API key.429 Too Many Requests: Rate limit or quota exceeded. See Quotas & Limits for how to handle this.
Make sure your application gracefully handles these errors to avoid disruptions.
Best Practices
- Store keys securely: Use environment variables or secure vaults instead of hard-coding API keys in your application.
- Rotate keys periodically: Periodically rotate your API keys to minimize potential security risks.
- Revoke compromised keys immediately: If an API key is compromised, revoke it immediately via the dashboard and generate a new one.
Need Help?
If you have questions or encounter issues, please reach out to our support team at support@safe.global.